1.17.2. Configure Service Application Associations
When you click the
Configure Service Application Associations link from Central
Administration, you are presented with the Service Applications
Associations interface shown in Figure 18, which allows you to associate the Web application or service application to an application proxy group.
When you click the Web Application link on this page, you will see a list of associated service
applications, and the service applications that are currently
associated with the Web application link you clicked are checked. To
modify a service application associated with the Web application, select
Custom from the drop-down menu at the top of the page and select the
service application check boxes for the service applications that you
want to associate with the Web application.
The Application Proxy
Group column indicates which application proxy group is associated with
each of the Web applications listed in the Service Application
Association interface.
1.18. Databases
When you create a Web
application, you specify the database that will be associated with it.
By default, there is only one database associated with a Web
application, but each Web application is capable of having multiple
databases associated with it.
1.18.1. Manage Content Databases
You can use the Manage
Content Databases interface to create, configure, and even delete the
content databases associated with a Web application. The default
settings for each content database has a maximum limit of 15,000 site
collections, with a default warning limit of 9000 site collections. This
warning limit notifies farm administrators when the database has
exceeded 9000 site collections. However, these default settings can be
modified to different settings as shown for the WSS_Content database in Figure 19. This modification allows you to control the size of your databases.
This interface also
indicates the number of site collections currently contained in each
database, as well as the status of the database. By creating
additional databases, you can control database growth by spreading the
location of site collections across multiple databases. You could then
limit the total number of site collections each database can hold to as
little as one site collection per database.
|
If a Web application
has multiple databases and you create a new site collection, the
database with the most available site collection capacity will receive
the new site collection by default. For instance, if a database called Wss_content1_db has a maximum setting of 500 and currently contains 100 site collections, and another database called Wss_content2_db
also has a maximum setting of 500 but currently contains only 50 site
collections, when you create a new site collection, Wss_content2_db will
receive the new site collection because it currently has fewer site
collections. In fact, the next several site collections you create will
also be stored in Wss_content2_db, until that database reaches the same
number of site collections (100) as Wss_content1_db contains. However,
if you want to control which database receives a newly created site
collection, set all other databases for that Web application to Offline
prior to creating the new site collection. This action will force the
site collection into the only database with the database status of
Ready. Remember to return the other databases to Ready after you create
the new site collection so that when future site collections are
created, they will be populated in the database with the most available
site collection capacity.
|
You can add other databases
by clicking the Add A Content Database link in the Manage Content
Databases interface. Furthermore, you can configure your existing
databases by clicking the name of the database, which allows you to
perform the following actions.
Change the database
status between Ready and Offline; when the status is Offline, no new
site collections can be added to the database.
View the Database Versioning And Status section to check the status and version of the database.
Specify a failover server.
Modify the maximum number of site collections the database can contain.
Modify the number of site collections the database can contain before administrators are warned.
Specify which search server the database is associated with.
Remove the content database from SQL Server.
Specify which server will be running the timer jobs associated with the database.
1.18.2. Specify the default database server
The SQL server
configured on the Default Database Server page indicates the default
location where all new content databases will be created. If you move
your SharePoint SQL Server instance to a new server, or if you create a
named instance of SQL Server that is going to host all of your content
databases, you can specify the new SQL Server instance on this screen.
However, when you create a new Web application, you can still specify a database server other than the default server defined here.
1.18.3. Configure the data retrieval service
When any connections are established to SharePoint 2010, they require the use of data services such as Simple Object Access Protocol (SOAP), Object Linking and Embedding, Database (OLEDB), Extensible Markup Language (XML), and Windows
SharePoint Services to allow data consumers and data sources to
communicate with each other. These services are Web services that return
XML data from
different data sources or manipulate data against those data sources.
This Data Retrieval Service page is used to configure the communication
and connectivity options associated with the data retrieval service.
